Bingo !!! It works !!!
After figuring out that there was not a single application that i had to depend on Windows for, I decided to move to a dual boot machine with SuSE 10.1 installed on a new partition. Surprise !!! Surprise !!! SuSE 10.1 was hanging at install time, when i was selecting my own set of packages that I wanted to install. It would fail while calculating the package dependencies, and the machine would hang up for 30 minutes [ well i gave up after 30 minutes and rebooted ]. Thats when it struck me that it was actually the low RAM that i had on my machine that was causing this problem. After upgrading to 512MB RAM, installation was just a piece of cake and all was up and running fine.
The first thing that i wanted to do was connect to a Solaris machine and run workshop to study some class graphs in the code. I telnet to a remote host [ yeah, its a secure internal network, so we are still on telnet ], export DISPLAY to my local machine, and start workshop, and i get ...
Could not connect to display ip:0.0
I tried shutting down the firewall assuming it was some security restriction, and it still failed. Changed the file permissions for some XAuth files and subdirectories and it still didnt work !!! Atleast 10 pairs of eyes saw the problem and all tried the same old xhost + thing and restart X, xfs, and almost everything starting with x :D It still did not budge. I had spent almost 4 weeks booting between windows and Linux alternately every week, using Windows only when it was really necessary to launch some X windows from other remote machines.
Well, the reason was quite simple. We were all fixing it in the wrong place. After some googling by one of my friends, who assumed that I was on KDE, i found saw some light at the end of the long tunnel. I was on GNOME. I tried figuring out the similar things for GNOME and i hit upon the solution.
I had to modify gdm.conf [ well .. it will be somewhere under /etc, do a find on your distro ], and enable a value "DisableTCP=false" and then also set the "Port=177". These 2 changes, and i was able to launch X windows from remote machines on my local desktop and I was on top of the world feeling as if I had solved the world's most difficult problem :D [ well, in a way, it was so for my small world ]
For the convenience of others, here is the unified diff of the original and modified gdm.org files.
diff -u /etc/opt/gnome/gdm/gdm.conf.org /etc/opt/gnome/gdm/gdm.conf
--- /etc/opt/gnome/gdm/gdm.conf.org
+++ /etc/opt/gnome/gdm/gdm.conf
@@ -202,7 +202,7 @@
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
-#DisallowTCP=true
+DisallowTCP=false
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
@@ -247,7 +247,7 @@
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
-#Port=177
+Port=177
# Willing script, none is shipped, X11's one is used by default. If
# none is present we'll send hostname system id. But if you supply
# something here, the output of this script will be sent as status of
The first thing that i wanted to do was connect to a Solaris machine and run workshop to study some class graphs in the code. I telnet to a remote host [ yeah, its a secure internal network, so we are still on telnet ], export DISPLAY to my local machine, and start workshop, and i get ...
Could not connect to display ip:0.0
I tried shutting down the firewall assuming it was some security restriction, and it still failed. Changed the file permissions for some XAuth files and subdirectories and it still didnt work !!! Atleast 10 pairs of eyes saw the problem and all tried the same old xhost + thing and restart X, xfs, and almost everything starting with x :D It still did not budge. I had spent almost 4 weeks booting between windows and Linux alternately every week, using Windows only when it was really necessary to launch some X windows from other remote machines.
Well, the reason was quite simple. We were all fixing it in the wrong place. After some googling by one of my friends, who assumed that I was on KDE, i found saw some light at the end of the long tunnel. I was on GNOME. I tried figuring out the similar things for GNOME and i hit upon the solution.
I had to modify gdm.conf [ well .. it will be somewhere under /etc, do a find on your distro ], and enable a value "DisableTCP=false" and then also set the "Port=177". These 2 changes, and i was able to launch X windows from remote machines on my local desktop and I was on top of the world feeling as if I had solved the world's most difficult problem :D [ well, in a way, it was so for my small world ]
For the convenience of others, here is the unified diff of the original and modified gdm.org files.
diff -u /etc/opt/gnome/gdm/gdm.conf.org /etc/opt/gnome/gdm/gdm.conf
--- /etc/opt/gnome/gdm/gdm.conf.org
+++ /etc/opt/gnome/gdm/gdm.conf
@@ -202,7 +202,7 @@
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
-#DisallowTCP=true
+DisallowTCP=false
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
@@ -247,7 +247,7 @@
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
-#Port=177
+Port=177
# Willing script, none is shipped, X11's one is used by default. If
# none is present we'll send hostname system id. But if you supply
# something here, the output of this script will be sent as status of
No comments:
Post a Comment